src/vs/sessions/contrib/aquarium/browser/aquariumOverlay.ts:343

• Food drops are wired to EventType.MOUSE_DOWN. On iOS this event doesn’t fire (pointer events are used), so users won’t be able to drop food. Please use addDisposableGenericMouseDownListener (or pointer events) for cross-platform input.

	store.add(addDisposableListener(mainContainer, EventType.MOUSE_DOWN, (e: MouseEvent) => {
		// Only spawn food on plain left clicks against background-ish surfaces.
		if (e.button !== 0) {
			return;
		}

src/vs/sessions/contrib/aquarium/browser/aquariumOverlay.ts:324

• createActiveAquarium() mixes targetWindow.document (for fish) with the global document (for water, fishLayer, foodLayer). In multi-window scenarios this can create nodes in the wrong document/realm. Prefer consistently using targetWindow.document.createElement(...) here so the overlay is built in the same window as mainContainer.

	const water = document.createElement('div');
	water.className = 'agents-aquarium-water';
	// Insert as the FIRST child so all subsequent chat bar content paints over it.
	chatBar.insertBefore(water, chatBar.firstChild);
	store.add(toDisposable(() => water.remove()));

	const fishLayer = document.createElement('div');
	fishLayer.className = 'agents-aquarium-fish-layer';
	water.appendChild(fishLayer);

	const foodLayer = document.createElement('div');
	foodLayer.className = 'agents-aquarium-food-layer';
	water.appendChild(foodLayer);

src/vs/sessions/contrib/aquarium/browser/aquariumOverlay.ts:470

• spawnFood() uses the global document.createElement('div') even though this aquarium instance is scoped to targetWindow. For consistency (and to avoid cross-window DOM issues), use targetWindow.document.createElement(...) here too.

		const el = document.createElement('div');
		el.className = 'agents-aquarium-food';
		el.style.transform = `translate(${fx}px, ${fy}px)`;
		foodLayer.appendChild(el);
		food.push({ element: el, x: fx, y: fy, vy: randomBetween(20, 35) });

src/vs/sessions/contrib/aquarium/browser/aquariumOverlay.ts:406

• Disposing the shared SVG defs container as part of each aquarium instance's disposal is unsafe when there can be overlap (e.g., deactivate triggers an exit animation + delayed dispose, then activate creates a new aquarium before the delay completes). When the old instance disposes it will remove defs still referenced by the new fish. Consider ref-counting the shared defs (increment on activation, decrement on disposal) or tying defs lifetime to AquariumOverlay instead of the per-activation store.

		// Tear down the shared SVG defs container along with the last
		// active aquarium so we don't leak it across reloads.
		disposeSharedFishDefs();
	}));

src/vs/sessions/contrib/aquarium/browser/aquariumOverlay.ts:381

• Listening for 'scroll' on targetWindow with { capture: true } will fire for scrolls anywhere in the document (since scroll doesn't bubble but is capturable). Calling getBoundingClientRect() in updateBounds() on every scroll can force frequent layouts and cause jank. Consider throttling this (e.g. schedule one updateBounds() per animation frame), or scope the listener to the specific scroll container(s) that can actually move the chat bar.

	// Listen on the main container so we always know cursor position even
	// when over the chat input (water has pointer-events:none).
	store.add(addDisposableListener(targetWindow, EventType.RESIZE, updateBounds, { passive: true }));
	store.add(addDisposableListener(targetWindow, 'scroll', updateBounds, { passive: true, capture: true }));

src/vs/sessions/contrib/aquarium/browser/aquariumOverlay.ts:447

• When prefers-reduced-motion is enabled, the RAF loop continues to schedule frames indefinitely even though updateFood/updateFish are skipped. This still consumes CPU/battery. Consider not starting the RAF loop at all (or stopping it) when reduceMotion is true, and keep the aquarium in its initial static state.

	const reduceMotion = targetWindow.matchMedia?.('(prefers-reduced-motion: reduce)').matches ?? false;
	let lastFrame = performance.now();
	let rafDisposable: IDisposable | undefined;

	const tick = () => {
		const now = performance.now();
		const dtMs = Math.min(now - lastFrame, 100); // clamp big stalls
		const dt = dtMs / 1000;
		lastFrame = now;

		// Skip work when window is hidden (RAF stays alive lazily).
		const visible = targetWindow.document.visibilityState !== 'hidden';
		if (visible && !reduceMotion) {
			updateFood(dt);
			updateFish(dt);
		}

		rafDisposable = scheduleAtNextAnimationFrame(targetWindow, tick);
	};

src/vs/sessions/contrib/aquarium/browser/aquariumOverlay.ts:291

• The aquarium DOM is purely decorative, but the created elements (water, fish/food layers) are not marked as such. Add aria-hidden="true" (and/or role="presentation") to these containers (and likely individual fish/food elements) so they don't appear in the accessibility tree.

	const water = doc.createElement('div');
	water.className = 'agents-aquarium-water';
	// First child so subsequent chat bar content paints over it.
	chatBar.insertBefore(water, chatBar.firstChild);
	store.add(toDisposable(() => water.remove()));

	const fishLayer = doc.createElement('div');
	fishLayer.className = 'agents-aquarium-fish-layer';
	water.appendChild(fishLayer);

	const foodLayer = doc.createElement('div');
	foodLayer.className = 'agents-aquarium-food-layer';
	water.appendChild(foodLayer);

src/vs/sessions/contrib/aquarium/browser/aquariumOverlay.ts:276

• createActiveAquarium returns a no-op aquarium when the chat bar container isn't available/visible, but activate() still treats it as active (context key set, toggle shows active, and user preference may be persisted). This can leave the UI in an “enabled but nothing happens” state. Consider having createActiveAquarium return undefined (or throw a known error) when the chat bar isn't ready, and have activate() bail out without updating context/button state (optionally retry once the chat bar becomes visible).

	// Host inside the chat bar so chat input UI naturally paints on top —
	// no z-index gymnastics required.
	const chatBar = layoutService.getContainer(targetWindow, Parts.CHATBAR_PART);
	if (!chatBar || !layoutService.isVisible(Parts.CHATBAR_PART, targetWindow)) {
		return {
			dispose: () => store.dispose(),
			exit: () => { store.dispose(); return store; },
		};
	}